In-device coexistence between radios

ABSTRACT

A method for facilitating in-device coexistence between radios is provided. The method can include a processor implemented on the wireless communication device defining a coexistence policy for a first radio and a second radio co-located on the wireless communication device; and providing the coexistence policy to a coexistence management controller on the first radio via an interface between the processor and the first radio. The method can further include the second radio providing state information for the second radio to the first radio via an interface between the first radio and the second radio. The method can additionally include the coexistence management controller on the first radio using the state information to control operation of the first radio in accordance with the coexistence policy to mitigate interference with the second radio.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Patent ApplicationNo. 61/655,994, filed on Jun. 5, 2012, which is incorporated herein inits entirety by reference.

FIELD OF THE DESCRIBED EMBODIMENTS

The described embodiments relate generally to wireless communicationsand more particularly to facilitating in-device coexistence betweenradios.

BACKGROUND

Many modern wireless communication devices include multiple radios.These multiple radios may be used by the device to concurrentlycommunicate via multiple wireless communication technologies. In manyinstances, wireless communication technologies used by a device usechannel bands that may interfere with each other. In such instances,energy from a band used by one technology can leak into a band used byanother technology. This energy leakage can raise the noise floor andcause a problem known as desense. In many instances, desense cannegatively impact the use of certain channel bands and, in severe cases,can render certain channel bands unusable. Accordingly, interferencethat can result in desense poses a problem for in-device coexistence ofmultiple radios using disparate wireless communication technologies.

A particularly troublesome desense problem can result in a scenario inwhich a one radio emits a transmission via a first wirelesscommunication technology, referred to as an aggressor wirelesscommunication technology, or aggressor technology, while another radioreceives data via a second wireless communication technology, referredto as a victim wireless communication technology, or victim technology.Data receipt via the victim technology can be damaged by the aggressortransmission, particularly in instances in which the radio using theaggressor technology uses a relatively high transmission power. In thisregard, received packet errors, or even complete deafening of the radiousing the victim technology receiver can result from the interferencethat can be caused by the aggressor technology transmission. For exampletransmission of a cellular signal by a first radio on a device at a timewhen a Bluetooth or wireless local area network (WLAN) signal isreceived by a second radio on the device can deafen the second radio,causing errors and, in some cases, loss of connection.

SUMMARY OF THE DESCRIBED EMBODIMENTS

Some embodiments disclosed herein provide an architecture andcorresponding methods, apparatuses, and computer program products forfacilitating in-device coexistence between radios. For example, someexample embodiments facilitate coexistence between a cellular radio anda connectivity radio, such as a connectivity radio using an Industrial,Scientific, and Medical (ISM) band. More particularly, some exampleembodiments provide an architecture in which a host processor can beconfigured to define a coexistence policy for two or more radios thatcan be implemented on a wireless communication device. The coexistencepolicy of some example embodiments can define a priority between radiosgiven a present use case context such that a radio can be given priorityover another radio based on a given use case context. The host processorcan provide the coexistence policy to the radios via an interfacebetween the host processor and the radios.

The radios can be configured to exchange state information via aseparate interface between the radios. The interface between the radioscan be a higher speed interface, which can facilitate real time exchangeof state information between the radios. The state information can, forexample, be indicative of interference conditions experienced by aradio, operating state information indicative of whether a radio istransmitting or receiving data during a given time period, and/or thelike. In this regard, state information that can change frequently(e.g., in real time) can be exchanged between radios via an interfacethat can facilitate relatively high speed communication between radios.In this regard, some example embodiments partition information that canbe used by a radio to make a decision for controlling radio operation tomitigate in-device interference into non-real time information that doesnot change relatively frequently, such as coexistence policies, andstate information for the co-located radio(s) that can change frequentlyover time. The coexistence policies and/or other non-real timeinformation that may not change with a great deal of regularity canaccordingly be communicated between a host processor and radios via aslower speed interface(s) and/or shared interface via which otherinformation can be communicated without clogging a higher speed, directinterface between radios.

A radio in accordance with some example embodiments can use stateinformation received from another radio to control radio operation inaccordance with the coexistence policy provided by the host processor.In this regard, a radio can have knowledge of conditions experienced byand/or activities being performed by a co-located radio based on thestate information and can use this knowledge to determine whether tomodify radio operation to mitigate interference with the co-locatedradio in accordance with the coexistence policy at a given time.

This Summary is provided merely for purposes of summarizing some exampleembodiments so as to provide a basic understanding of some aspects ofthe disclosure. Accordingly, it will be appreciated that the abovedescribed example embodiments are merely examples and should not beconstrued to narrow the scope or spirit of the disclosure in any way.Other embodiments, aspects, and advantages will become apparent from thefollowing detailed description taken in conjunction with theaccompanying drawings which illustrate, by way of example, theprinciples of the described embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

The described embodiments and the advantages thereof may best beunderstood by reference to the following description taken inconjunction with the accompanying drawings. These drawings are notnecessarily drawn to scale, and in no way limit any changes in form anddetail that may be made to the described embodiments by one skilled inthe art without departing from the spirit and scope of the describedembodiments.

FIG. 1 illustrates an example of adjacent channel interference that canbe addressed by some example embodiments.

FIG. 2 illustrates a block diagram of a wireless communication device inaccordance with some example embodiments.

FIG. 3 illustrates an architecture for facilitating in-devicecoexistence between radios in accordance with some example embodiments.

FIG. 4 illustrates an example system in which some example embodimentscan be implemented to facilitate in-device coexistence between radios.

FIG. 5 illustrates a flowchart according to an example method that canbe performed by a wireless communication device for facilitatingin-device coexistence between radios according to some exampleembodiments.

FIG. 6 illustrates a flowchart according to an example method that canbe performed by a processor of a wireless communication device forfacilitating in-device coexistence between radios according to someexample embodiments.

FIG. 7 illustrates a flowchart according to another example method thatcan be performed by a processor of a wireless communication device forfacilitating in-device coexistence between radios according to someexample embodiments.

FIG. 8 illustrates a flowchart according to an example method that canbe performed by a radio for facilitating in-device coexistence betweenradios according to some example embodiments.

FIG. 9 illustrates a flowchart according to another example method thatcan be performed by a radio for facilitating in-device coexistencebetween radios according to some example embodiments.

DETAILED DESCRIPTION OF SELECTED EMBODIMENTS

Some example embodiments address an in-device coexistence problembetween radios using disparate wireless communication technologies. Inthis regard, wireless communication devices often include multipleradios, each of which can implement one or more disparate wirelesscommunication technologies, which coexist on the device. For example, acellular radio, such as a Long Term Evolution (LTE) radio, can coexiston a device along with one or more connectivity radios, such as aBluetooth radio, WLAN (e.g., Wi-Fi) radio, and/or the like. Inembodiments including a Wi-Fi Radio, the Wi-Fi radio can implement anInstitute of Electrical and Electronics Engineers (IEEE) 802.11technology, such as one or more of: IEEE 802.11a; IEEE 802.11b; IEEE802.11g; IEEE 802.11-2007; IEEE 802.11n; IEEE 802.11-2012; IEEE802.11ac; or other present or future developed IEEE 802.11 technologies.The connectivity radio can use an ISM band. For example, Bluetooth canoperate in the 2.4 GHz ISM band, while a WLAN radio can operate in the2.4 GHz and/or 5 GHz ISM bands. The cellular radio and/or connectivityradio(S) can further coexist with a Global Navigation Satellite System(GNSS) radio, such as a Global Positioning System (GPS) radio, GLONASSradio, and/or other GNSS radio, which can operate in the 1.6 GHz band.

Concurrent operation of multiple radios on a wireless communicationdevice can result in interference between radios. In this regard,interference can result from a transmission emitted by a radio using anaggressor technology while a radio is receiving data via a victimtechnology. In such situations, the aggressor technology transmissionscan inhibit data reception via the victim technology, potentiallyresulting in received data errors, or in extreme cases, even completelydeafening the victim technology receiver. This radio frequency (RF)interference can be caused by a number of side effects that can resultfrom concurrent radio operation on a device.

For example, RF interference can result from adjacent channelinterference (ACI), in which transmit energy spills over into adjacentbands. FIG. 1 illustrates an example of ACI that can be addressed bysome example embodiments. In this regard, one or more cellular bands canbe adjacent to an ISM band that can be used by a connectivity radio. Inthe example of FIG. 1, LTE band 40 using time-division duplexing (TDD)102 can operate in the 2300-2400 MHz band range, while LTE band 7 usingfrequency-division duplexing (FDD) for uplink (UL) communications 104can operate in the 2500-2570 MHz band range. The LTE bands 102 and 104can act as aggressor bands such that transmissions via these bands caninterfere with reception via connectivity radios operating in theadjacent 2400 GHz ISM band. For example, as illustrated in FIG. 1, aBluetooth radio operating in the 2402-2480 MHz band 106 and a Wi-Firadio operating in the 2400-2483.5 MHz band 108 can suffer as victimsfrom adjacent channel interference resulting from the LTE bands 102 and104, as transmit energy from LTE bands 102 and 104 can spill over intothe bands 106 and 108 and can desense the Bluetooth and Wi-Fi radios,potentially interfering with data reception by the Bluetooth and Wi-Firadios.

As another example, intermodulation distortion can result in RFinterference that can harm reception by a radio. In this regard,harmonics can be generated when two or more transmit frequencies “mix”with each other due to non-linearity. For example, cellular bands 5and/or 8 can mix with 2.4 GHz ISM band transmissions to desense a GNSSreceive band. As still a further example, RF interference can resultfrom harmonic distortion in which harmonics can be generated from asingle transmit frequency due to a non-linearity.

For example, when a device communicates concurrently via cellularcommunications and a lower powered communication technology, such as anIEEE 802.15 wireless personal area network (PAN) communicationtechnology (e.g., Bluetooth and/or other wireless PAN communicationtechnology) or WLAN technology, which can, for example, utilize an ISMband, cellular transmissions can prevent data reception via the lowerpowered technology. Some example embodiments facilitate in-devicecoexistence between wireless communication technologies by mitigatingsuch in-device interference conditions.

Several example embodiments described herein can facilitate in-devicecoexistence between radios by mitigating the effects of such RFinterference conditions. In this regard, some example embodimentsprovide an architecture and corresponding methods, apparatuses, andcomputer program products for facilitating in-device coexistence betweenradios. More particularly, some example embodiments provide anarchitecture in which a host processor can be configured to define acoexistence policy for two or more radios (e.g., a cellular radio, aconnectivity radio(s), a GNSS radio, and/or the like) that can beimplemented on a wireless communication device. The coexistence policyof some example embodiments can define a priority between radios given apresent use case context such that a radio can be given priority overanother radio based on a given use case context. The host processor canprovide the coexistence policy to the radios via an interface betweenthe host processor and the radios.

The radios of such example embodiments can be configured to exchangestate information via a separate interface between the radios. Theinterface between the radios can be a higher speed interface, which canfacilitate real time exchange of state information between the radios.The state information can, for example, be indicative of interferenceconditions experienced by a radio, operating state informationindicative of whether a radio is transmitting or receiving data during agiven time period, and/or the like. As such, state information that canchange frequently and/or which requires low-latency communication (e.g.,in real time) can be exchanged between radios via an interface that canfacilitate relatively high speed communication between radios. In thisregard, some example embodiments partition information that can be usedby a radio to make a decision for controlling radio operation tomitigate in-device interference into non-real time information that doesnot change relatively frequently, such as coexistence policies, andstate information for the co-located radio(s) that can change frequentlyover time. The coexistence policies and/or other non-real timeinformation that may not change frequently can accordingly becommunicated between a host processor and radios via a slower speedinterface(s) and/or shared interface via which other information can becommunicated without clogging a higher speed, direct interface betweenradios.

A radio in accordance with some example embodiments can use stateinformation received from another radio to control radio operation inaccordance with the coexistence policy provided by the host processor.In this regard, a radio can have knowledge of conditions experienced byand/or activities being performed by a co-located radio based on thestate information and can use this knowledge to determine whether tomodify radio operation to mitigate interference with the co-locatedradio in accordance with the coexistence policy at a given time. Thus,for example, an aggressor radio, such as a cellular radio, can know fromthe state information whether a victim radio, such as a Bluetooth radio,is receiving data at a given time and, if the victim radio is receivingdata at a given time and has a higher defined priority based on thecoexistence policy, the aggressor radio can take action, such as backingoff transmission power, to mitigate interference with data reception bythe victim radio. If, however, the victim radio is not receiving data ata given time, the aggressor radio can know based on the stateinformation that it can transmit data without regard for the victimradio at that point in time, even if the victim radio has a higherpriority based on the coexistence policy.

Referring now to FIG. 2, FIG. 2 illustrates a block diagram of awireless communication device 200 in accordance with some exampleembodiments. The wireless communication device 200 can be any deviceincluding two or more co-located radios, which can enable the device tocommunicate via multiple wireless communication technologies. By way ofnon-limiting example, the wireless communication device 200 can be amobile phone, tablet computing device, laptop computer, or othercomputing device that can include multiple radios. It will beappreciated that the components, devices or elements illustrated in anddescribed with respect to FIG. 2 below may not be mandatory and thussome may be omitted in certain embodiments. Additionally, someembodiments can include further or different components, devices orelements beyond those illustrated in and described with respect to FIG.2.

In some example embodiments, the wireless communication device 200 caninclude processing circuitry 210 that is configurable to perform actionsin accordance with one or more example embodiments disclosed herein. Inthis regard, the processing circuitry 210 can be configured to performand/or control performance of one or more functionalities of thewireless communication device 200 in accordance with various exampleembodiments, and thus can provide means for performing functionalitiesof the wireless communication device 200 in accordance with variousexample embodiments. The processing circuitry 210 may be configured toperform data processing, application execution and/or other processingand management services according to one or more example embodiments. Insome embodiments, the wireless communication device 200 or a portion(s)or component(s) thereof, such as the processing circuitry 210, caninclude one or more chips, or one or more chipsets. The processingcircuitry 210 and/or one or more further components of the wirelesscommunication device 200 can therefore, in some instances, be configuredto implement an embodiment on a single chip or chipset.

In some example embodiments, the processing circuitry 210 can include aprocessor 212 and, in some embodiments, such as that illustrated in FIG.2, can further include memory 214. The processing circuitry 210 can bein communication with or otherwise control a coexistence scenariomanager 216 and two or more radios that can be implemented on thewireless communication device 200, including a first radio 218 andsecond radio 220.

The processor 212 can be embodied in a variety of forms. For example,the processor 212 can be embodied as various hardware-based processingmeans such as a microprocessor, a coprocessor, a controller or variousother computing or processing devices including integrated circuits suchas, for example, an ASIC (application specific integrated circuit), anFPGA (field programmable gate array), some combination thereof, or thelike. The processor 212 of some example embodiments can be a hostprocessor configured to serve as a host for controlling or otherwisefacilitating operation of two or more device radios, such as the firstradio 218 and second radio 220. In some example embodiments, theprocessor 212 can be an application processor. Although illustrated as asingle processor, it will be appreciated that the processor 212 cancomprise a plurality of processors. The plurality of processors can bein operative communication with each other and can be collectivelyconfigured to perform one or more functionalities of the wirelesscommunication device 200 as described herein. In some exampleembodiments, the processor 212 can be configured to execute instructionsthat can be stored in the memory 214 or that can be otherwise accessibleto the processor 212. As such, whether configured by hardware or by acombination of hardware and software, the processor 212 capable ofperforming operations according to various embodiments while configuredaccordingly.

In some example embodiments, the memory 214 can include one or morememory devices. Memory 214 can include fixed and/or removable memorydevices. In some embodiments, the memory 214 can provide anon-transitory computer-readable storage medium that can store computerprogram instructions that can be executed by the processor 212. In thisregard, the memory 214 can be configured to store information, data,applications, instructions and/or the like for enabling the wirelesscommunication device 200 to carry out various functions in accordancewith one or more example embodiments. In some embodiments, the memory214 can be in communication with one or more of the processor 212,coexistence scenario manager 216, first radio 218, or second radio 220via a bus(es) for passing information among components of the wirelesscommunication device 200.

The wireless communication device 200 can further include coexistencescenario manager 216, which can be embodied as various means, such ascircuitry, hardware, a computer program product comprising a computerreadable medium (for example, the memory 214) storing computer readableprogram instructions executable by a processing device (for example, theprocessor 212), or some combination thereof. In some embodiments, theprocessor 212 (or the processing circuitry 210) can include, orotherwise control the coexistence scenario manager 216. As will bedescribed further herein below, the coexistence scenario manager 216 canbe configured to define a coexistence policy for two or more radios onthe wireless communication device 200, such as the first radio 218 andsecond radio 220, and can provide the coexistence policy to the radiosfor implementation.

As noted, the wireless communication device 200 can include a pluralityof co-located radios. Two such radios—the first radio 218 and secondradio 220—are illustrated by way of example in FIG. 2. It will beappreciated, however, that the wireless communication device 200 caninclude one or more further radios in some example embodiments. Theradios implemented on the wireless communication device 200 can eachimplement any respective wireless communication technology such that twoor more disparate wireless communication technologies can be implementedon the wireless communication device 200. For example, in some exampleembodiments, one or more radios on the wireless communication device200, such as one or more of the first radio 218 or second radio 220, canimplement a cellular communication technology, such as a Long TermEvolution (LTE) cellular communication technology, a Universal MobileTelecommunications System (UMTS) cellular communication technology, aGlobal System for Mobile Communications (GSM) cellular communicationtechnology, a Code Division Multiple Access (CDMA) cellularcommunication technology, or a CDMA 2000 cellular communicationtechnology, and/or the like. As a further example, in some exampleembodiments, one or more radios on the wireless communication device200, such as one or more of the first radio 218 or second radio 220, canbe a connectivity radio implementing a communications technology, suchas Bluetooth, Zigbee, and/or other wireless personal area network (PAN)technology; and/or Wi-Fi and/or other wireless local area network (WLAN)communication technology. In some example embodiments, in which one ormore of the first radio 218 or second radio 220 is a connectivity radio,the connectivity radio can implement a wireless communication technologyusing an ISM band. As still a further example, the wirelesscommunication device 200 of some example embodiments can include a GNSSradio. It will be appreciated, however, that the foregoing example radiotechnologies are provided by way of example, and not by way oflimitation, as various example embodiments support in-device coexistencebetween any two (or more) radios that use disparate wirelesscommunication technologies.

An interface 222 can be used to interface two or more radios, such asthe first radio 218 and second radio 220, on the wireless communicationdevice 200. The interface 222 can be separate from an interface(s)between the processor 212 and the first radio 218 and second radio 220.The interface 222 can be a higher speed interface than the interface(s)between the radios and processor 212, which can offer low latency toallow (e.g., on the order of microseconds) for communication of realtime state information between radios. The interface 222 of some exampleembodiments can be an interface dedicated to the exchange of informationbetween radios, which may not be used for communication of informationto or from non-radio components of the wireless communication device200. In some example embodiments, the interface 222 can be a directinterface linking the first radio 218 and second radio 220 (andpotentially one or more further radios). In some example embodiments,the interface 222 can be a Wireless Coexistence Interface (WCI), such asa WCI-2 interface, WCI-1 interface, or other type of WCI. It will beappreciated, however, that WCI interface types are but one example of aninterface that can be used to facilitate communication of stateinformation between radios, and any appropriate interface that can beused to interface two or more radios to support the exchange of stateinformation between radios can be used in addition to or in lieu of anWCI interface in accordance with some example embodiments.

In some example embodiments, radios implemented on the wirelesscommunication device 200 can include respective coexistence managementcontrollers. For example, a first radio coexistence managementcontroller 224 can be implemented on the first radio 218 and a secondradio coexistence management controller 226 can be implemented on thesecond radio 220. The coexistence management controllers (e.g., thefirst radio coexistence management controller 224 and the second radiocoexistence management controller 226) can be embodied as various means,such as circuitry, hardware, a computer program product comprisingcomputer readable program instructions stored on a computer readablemedium that can be implemented on a radio and executed by a processingdevice that can be implemented on a radio, or some combination thereof.

The coexistence scenario manager 216 can be configured to define acoexistence policy for radios implemented on the wireless communicationdevice 200, such as the first radio 218 and second radio 220. Thecoexistence policy can, for example define priority levels across deviceradios, such as cellular, GNSS, Bluetooth, Wi-Fi, and/or the like. Inthis regard, the coexistence scenario manager 216 can maintain a“global” view of the priority levels across the various radios. Thecoexistence policy can be defined based on a present use case context ofthe wireless communication device 200. For example, a differentcoexistence policy can be defined and implemented in a use case contextin which a user of a cellular phone is using a Bluetooth headset whileon an active cellular call than in a use case context in which a user isengaged in an active data session over a cellular connection. As such,use case context-based coexistence priority levels in accordance withsome example embodiments can change relatively slowly in non-real timeover time in response to event triggers.

The coexistence scenario manager 216 can be further configured to pushthe coexistence policy down to the device radios via an interface(s)between the processor 212 and the device radios. The interface(s)between the processor 212 and the first radio 218 and second radio 220can be a non-real time interface(s). Communication of the coexistencepolicy to the radios can be primarily event-triggered. In this regard,the coexistence policy can be changed in response to event triggers asthe use case context of the device changes over time, such as inresponse to user activity.

Implementation and execution of the coexistence policy can be performedby the coexistence management controllers on the radios based oncoordination amongst the radios via the interface 222. In this regard,the coexistence management controllers (e.g., the first radiocoexistence management controller 224 and the second radio coexistencemanagement controller 226) can be configured to perform measurements andexchange state information between the radios via the interface 222. Aswill be described further herein below, the state information caninclude an indication of an interference condition experienced by aradio, operating state information for a radio, and/or other informationthat can be used by a coexistence management controller to determinewhether to modify radio operation to mitigate interference with anotherradio in accordance with the coexistence policy at a given time.

A coexistence management controller, such as the first radio coexistencemanagement controller 224 and the second radio coexistence managementcontroller 226, on a radio can perform real-time actions to controlradio operation based on a coexistence policy defined by the coexistencescenario manager 216 and one or more of state information that can beprovided by a co-located radio or measurements that can be made by theradio. In this regard, a coexistence management controller can determinewhether to take corrective action to mitigate interference with aco-located radio in accordance with a coexistence policy based onmeasurements that can be made by the radio and/or state information thatcan be provided by the co-located radio.

As such, it will be appreciated that some example embodiments partitioninformation that can be used by a coexistence management controller,such as the first radio coexistence management controller 224 and thesecond radio coexistence management controller 226, to make a decisionfor controlling radio operation to mitigate in-device interference intonon-real time information that does not change relatively frequently,such as coexistence policies, and real time state information for theco-located radio(s) that can change frequently over time. Thecoexistence policies and/or other non-real time information that may notchange with a great deal of regularity can accordingly be communicatedto the first radio 218 and second radio 220 by the processor 212 via aslower speed interface(s) and/or shared interface (e.g., a shared bus)via which other information can be communicated between devicecomponents. Real time state information for the radios can becommunicated via the interface 222, which can offer lower latency forcommunication of state information that can change relatively frequently(e.g., in real time) between the radios to allow for coordinationbetween radios. As non-real time information can be provided to theradios via another interface(s), the interface 222 provision of thenon-real time information to the device radios does not clog theinterface 222 or otherwise cause a delay in communication of real timestate information between radios.

A coexistence management controller implemented on a radio, such as thefirst radio coexistence management controller 224 and the second radiocoexistence management controller 226, can use any appropriate techniqueto control radio operation to take corrective action so as to mitigateinterference with a co-located radio when determined to be appropriatein accordance with a coexistence policy. In this regard, a coexistencemanagement controller can use one or more hardware-based techniquesand/or one or more software-based techniques for reducing interference.

As an example of a hardware-based technique that can be used, acoexistence management controller in accordance with some exampleembodiments can be configured to modify filtering that can be applied totransmissions, such as by applying sharper filtering to aggressor radiotransmissions to reduce adjacent channel interference with a victimradio. As another example hardware-based technique that can be used by acoexistence management controller to mitigate interference, acoexistence management controller in accordance with some exampleembodiments can be configured to adjust a linearity of RF components ofan aggressor radio, such as by reducing or increasing linearity asappropriate, to mitigate the effects of intermodulation distortionand/or harmonic distortion interference with a victim radio.

As an example of a software-based technique that can be used, acoexistence management controller in accordance with some exampleembodiments can be configured to apply time domain sharing techniques tomitigate the effects of interference. In this regard, if a victim radiohas lower priority than an aggressor radio, the coexistence managementcontroller on the victim radio can avoid receiving data when anaggressor radio(s) is (are) transmitting. The coexistence managementcontroller on the victim radio can know whether the aggressor radio istransmitting at a given time based on state information that can beprovided by the aggressor radio (e.g., via interface 222) and/or basedon measurements that can be performed by the victim radio. Similarly, ifa victim radio is defined by the coexistence policy to have higherpriority than an aggressor radio during a particular time period and isreceiving data during the time period, the coexistence managementcontroller on the aggressor radio can avoid transmitting data during thevictim radio's high priority reception period. The coexistencemanagement controller on the aggressor radio can know whether the victimradio is receiving data during a time period based on state informationthat can be provided by the victim radio (e.g., via interface 222)and/or based on measurements that can be performed by the aggressorradio.

As another example of a software-based technique that can be used, acoexistence management controller in accordance with some exampleembodiments can be configured to apply frequency domain exclusiontechniques to mitigate interference with a co-located radio. Forexample, a coexistence management controller on a victim radio can beconfigured to avoid reception on a frequency channel(s) affected byaggressor radio transmissions, if avoiding reception on the affectedchannel(s) is possible. The coexistence management controller on thevictim radio can, for example, have knowledge of a frequency channelaffected by aggressor radio transmissions based on measurements that canbe performed by the victim radio. The channel(s) affected by theaggressor transmissions can, for example, be the channel(s) within aband used by the victim radio immediately adjacent to a band used by theaggressor radio. In some example embodiments, the coexistence managementcontroller on the victim radio can be configured to apply frequencydomain exclusion techniques during periods which the aggressor radio isknown by the victim radio to be transmitting. In this regard, thecoexistence management controller on the victim radio can know whetherthe aggressor radio is transmitting at a given time based on stateinformation that can be provided by the aggressor radio (e.g., viainterface 222) and/or based on measurements that can be performed by thevictim radio.

A coexistence management controller on an aggressor radio can, forexample, be configured to apply frequency domain exclusion techniques toavoid transmission on a channel(s) that can be more damaging to a victimradio, if avoiding transmission on the channel(s) is possible. Thechannel(s) that can be more damaging to the victim radio can, forexample, be the channel(s) within a band used by the aggressor radioimmediately adjacent to a band used by the victim radio. In some exampleembodiments, the coexistence management controller on the aggressorradio can be configured to apply frequency domain exclusion techniquesduring periods which the victim radio is known by the aggressor radio tobe receiving data. In this regard, the coexistence management controlleron the aggressor radio can know whether the victim radio is receiving ata given time based on state information that can be provided by thevictim radio (e.g., via interface 222) and/or based on measurements thatcan be performed by the aggressor radio.

As a further example of a software-based technique that can be used, acoexistence management controller in accordance with some exampleembodiments can be configured to apply power domain exclusion techniquesto mitigate interference with a co-located radio. For example, if thereare multiple aggressor radios on a device, a coexistence managementcontroller on a first aggressor radio can avoid transmittingconcurrently with the second aggressor radio so as to limit the totaltransmission power emitted by the device and/or to avoid causingintermodulation distortion to mitigate interference with a victim radio.In this example, the coexistence policy may accord a lower priority tothe first aggressor radio than to the second aggressor radio and thevictim radio such that the coexistence management controller on thefirst aggressor radio can back off and avoid transmitting, therebyyielding to transmission by the first aggressor radio and mitigatinginterference with the victim reference. The coexistence managementcontroller on the first aggressor radio can determine to avoidtransmitting based on knowledge of whether the second aggressor radio istransmitting at a given time and/or whether the victim radio isreceiving at a given time. In this regard, the coexistence managementcontroller on the first aggressor radio can know whether the secondaggressor radio is transmitting and/or whether the victim radio isreceiving during a given period of time based on state information thatcan be provided by the second aggressor radio and/or by the victim radio(e.g., via interface 222) and/or based on measurements that can beperformed by the first aggressor radio.

As another example of a power domain exclusion technique that can beimplemented by the coexistence management controller of an aggressorradio is backing off transmission power of the aggressor radio if thevictim radio is receiving. In this regard, limiting the transmissionpower can reduce a level of interference with reception by the victimradio. The coexistence management controller can know whether the victimradio is receiving during a given period of time based on stateinformation that can be provided by the victim radio (e.g., viainterface 222) and/or based on measurements that can be performed by theaggressor radio.

FIG. 3 illustrates an example architecture for facilitating in-devicecoexistence between radios in accordance with some example embodiments.The architecture can include a HOST 302, which can be embodied as anapplication processor. The HOST 302 can, for example, be an embodimentof the processor 212 and/or of the processing circuitry 210. Thearchitecture can further include a plurality of radios. In the exampleof FIG. 3, the architecture can include a cellular radio 304, a GNSSradio 306, and a Bluetooth (BT)/Wi-Fi combo radio 308. It will beappreciated, however, that the combination of radios illustrated in FIG.3 is illustrated by way of example, and not by way of limitation. Inthis regard, one or more of the cellular radio 304, GNSS radio 306, andBT/Wi-Fi combo radio 308 can be omitted in some example embodiments.Further, in some example embodiments, the architecture can include oneor more other radios in addition to or in lieu of the radios illustratedin and described with respect to FIG. 3. Moreover, the use of a BT/Wi-Ficombo radio is by way of example, and some example embodiments caninclude a standalone Bluetooth radio and/or a standalone Wi-Fi radio. Assuch, it will be appreciated that the architectural structure andcorresponding techniques illustrated in and described with respect toFIG. 3 can be applied mutatis mutandis to any combination of radios thatcan be implemented on a wireless communication device.

The HOST 302 can include a coexistence scenario manager 310, which canbe responsible for defining coexistence policies for the device radiosand providing the coexistence policies to the device radios. In thisregard, the coexistence scenario manager 310 can, for example, be anembodiment of the coexistence scenario manager 216. One or moreapplications 312 can be running on the HOST 302. The coexistencescenario manager 310 can accordingly have knowledge of theapplication(s) 312 that are active at a given time. In some exampleembodiments, the coexistence scenario manger 310 can determinecorresponding use case state information for active applications. Inthis regard, the coexistence scenario manager 310 can leverage knowledgeof a state of applications 312 to derive a global view of the deviceusage and determine a present use case context for the device. Thecoexistence scenario manager 310 can be configured to define acoexistence policy for the device radios based at least in part on thepresent use case context. The coexistence policy can include adefinition of one or more priorities between device radios with respectto the use case context.

The coexistence scenario manager 310 can be configured to provide adefined coexistence policy to the device radios via respective radiomanager intermediaries that can be implemented on the HOST 302. Forexample, a cellular radio manager 314 can facilitate communicationbetween the coexistence scenario manager 310 and cellular radio 304. AGNSS radio manager 316 can facilitate communication between thecoexistence scenario manager 310 and GNSS radio 306. A BT radio manager318 can facilitate communication between the coexistence scenariomanager 310 and the BT portion of the BT/Wi-Fi combo radio 308. A Wi-Firadio manager 320 can facilitate communication between the coexistencescenario manager 310 and the Wi-Fi portion of the BT/Wi-Fi combo radio308.

The coexistence scenario manager 310 can be configured to use aninterface(s) 338 to provide a coexistence policy to the radios (e.g.,via the respective radio manager intermediaries 314-320). Theinterface(s) 338 can be a non-real time interface(s), which can be usedfor large message transfers, and which may have a delay on the order ofmilliseconds. The interface(s) 338 of some example embodiments can beshared by components of a wireless communication device in addition tothe HOST 302 and radios 304-308, and can be used for the communicationof data in addition to coexistence policies and/or other informationthat can be exchanged between the HOST 302 and the radios 304-308.

The cellular radio 304 can include a real time coex manager 322, whichcan be configured to implement and execute a coexistence policy definedby the coexistence scenario manager 310. In this regard, the real timecoex manager 322 can, for example, be an embodiment of a coexistencemanagement controller (e.g., the coexistence management controller 224or coexistence management controller 226) described with respect to FIG.2. The real time coex manager 322 can be configured to use radiomeasurements 324 that can be made by the cellular radio 304 and/or stateinformation received from the GNSS radio 306 and/or from the BT/Wi-Ficombo radio 308 via the real time interface 326 to make controldecisions for controlling the cellular radio 304 in accordance with thecoexistence policy so as to mitigate interference with the GNSS radio306 and/or with the BT/Wi-Fi Combo radio 308.

The real time interface 326 can be an interface offering a low latency,such as a delay on the order of microseconds, to allow for communicationof real time state information between radios to facilitate coordinationbetween radios in accordance with a coexistence policy defined andhanded down by the coexistence scenario manager 310. In some exampleembodiments, the real time interface 326 can be a WCI interface, such asa WCI-2 interface or WCI-1 interface. The real time interface 326 ofsome example embodiments can be an interface dedicated to the exchangeof information between radios, which may not be used for communicationof information to or from non-radio components.

The real time coex manager 322 can be further configured to providestate information for the cellular radio 304 to the GNSS radio 306and/or to the BT/Wi-Fi combo radio 308 via the real time interface 326.The state information can include any information about a state of thecellular radio 304 that can be used by the GNSS radio 306 and/or by theBT/Wi-Fi combo radio 308 to make determinations for radio operationcontrol in compliance with a coexistence policy defined by thecoexistence scenario manager 310. For example, the state information caninclude operating state information indicative of whether the cellularradio 304 is receiving or transmitting data during one or more timeperiods. The state information can additionally or alternatively includean indication of an interference condition that may be experienced bythe cellular radio 304, such as can be determined by the cellular radio304 based on the radio measurements 324.

The GNSS radio 306 can include a real time coex manager 328, which canbe configured to implement and execute a coexistence policy defined bythe coexistence scenario manager 310. In this regard, the real time coexmanager 328 can, for example, be an embodiment of a coexistencemanagement controller (e.g., the coexistence management controller 224or coexistence management controller 226) described with respect to FIG.2. The real time coex manager 328 can, for example, be configured to usemeasurements that can be made by the GNSSS radio 306 and/or stateinformation received from the cellular radio 304 and/or from theBT/Wi-Fi combo radio 308 via the real time interface 326 to make controldecisions for controlling the GNSS radio 306 in accordance with thecoexistence policy so as to mitigate interference with the cellularradio 304 and/or with the BT/Wi-Fi Combo radio 308.

The real time coex manager 328 can be further configured to providestate information for the GNSS radio 306 to the cellular radio 304and/or to the BT/Wi-Fi combo radio 308 via the real time interface 326.The state information can include any information about a state of theGNSS radio 306 that can be used by the cellular radio 304 and/or by theBT/Wi-Fi combo radio 308 to make determinations for radio operationcontrol in compliance with a coexistence policy defined by thecoexistence scenario manager 310. For example, the state information caninclude operating state information indicative of whether the GNSS radio306 is receiving or transmitting data during one or more time periods.The state information can additionally or alternatively include anindication of an interference condition that may be experienced by theGNSS radio 306, such as can be determined based on measurements that canbe made by the GNSS radio 306.

The BT/Wi-Fi combo radio 308 can include a real time coex manager 330,which can be configured to implement and execute a coexistence policydefined by the coexistence scenario manager 310. In this regard, thereal time coex manager 330 can, for example, be an embodiment of acoexistence management controller (e.g., the coexistence managementcontroller 224 or coexistence management controller 226) described withrespect to FIG. 2. The real time coex manager 330 can be configured touse radio measurements 332 that can be made by the BT/Wi-Fi combo radio308 and/or state information received from the cellular radio 304 and/orfrom the GNSS radio 306 via the real time interface 326 to make controldecisions for controlling the BT/Wi-Fi combo radio 308 in accordancewith the coexistence policy so as to mitigate interference with thecellular radio 304 and/or with the GNSS radio 306.

The real time coex manager 330 can be further configured to providestate information for the BT/Wi-Fi combo radio 308 to the cellular radio304 and/or to the GNSS radio 306 via the real time interface 326. Thestate information can include any information about a state of theBT/Wi-Fi combo radio 308 that can be used by the cellular radio 304and/or by the GNSS radio 306 to make determinations for radio operationcontrol in compliance with a coexistence policy defined by thecoexistence scenario manager 310. For example, the state information caninclude operating state information indicative of whether the BT/Wi-Ficombo radio 308 is receiving or transmitting data during one or moretime periods. The state information can additionally or alternativelyinclude an indication of an interference condition that may beexperienced by the BT/Wi-Fi combo radio 308, such as can be determinedby the BT/Wi-Fi combo radio 308 based on the radio measurements 332.

FIG. 4 illustrates an example system 400 in which some exampleembodiments can be implemented to facilitate in-device coexistencebetween wireless communication technologies. The system 400 can includea wireless communication device 402, which can, for example, be anembodiment of wireless communication device 200. The wirelesscommunication device 402 can be configured to engage in cellularcommunications, which can be supported by a base station 402. Forexample, the wireless communication device 402 can be configured toengage in communication via a Long Term Evolution (LTE) cellularcommunication technology, a Universal Mobile Telecommunications System(UMTS) cellular communication technology, a Global System for MobileCommunications (GSM) cellular communication technology, a Code DivisionMultiple Access (CDMA) cellular communication technology, or a CDMA 2000cellular communication technology, and/or other cellular communicationtechnology. The wireless communication device 402 can be furtherconfigured to engage in communications via an ISM band technology. Thus,for example, the wireless communication device 402 can engage inwireless communications with a device 408 via an ISM band network 406.For example, in embodiments in which the ISM band network 406 is aBluetooth network, the device 408 can be a Bluetooth headset or otherBluetooth device that can be interfaced with a wireless communicationdevice.

In context of the system 400, various embodiments, can be implemented onthe wireless communication device 402 to control operation of a cellularradio and/or ISM band radio(s) on the wireless communication device 402to mitigate interference between the device radios in accordance with acoexistence policy to facilitate in-device coexistence between cellularand ISM band radios. It will be appreciated, however, that system 400 isprovided merely by way of example. In this regard, as previously noted,some example embodiments facilitate in-device radio coexistencescenarios other than cellular and ISM band radio coexistence.

FIG. 5 illustrates a flowchart according to an example method that canbe performed by a wireless communication device for facilitatingin-device coexistence between radios according to some exampleembodiments. In this regard, FIG. 5 illustrates operations that can beperformed by the wireless communication device 200 and/or by thearchitecture illustrated in FIG. 3. The operations illustrated in anddescribed with respect to FIG. 5 can, for example, be performed tofacilitate in-device radio coexistence between cellular and ISM bandradios, such as within the context of the system 400.

Operation 500 can include the coexistence scenario manager 216 defininga coexistence policy for the first radio 218 and the second radio 220.The coexistence policy can, for example, define a priority between thefirst radio 218 and the second radio 220. In some example embodiments,the coexistence policy can be defined based at least in part on a usecase context of the wireless communication device, such that a differentcoexistence policy can be defined for a first use case context than fora second use case context.

Operation 510 can include the coexistence scenario manager 216 providingthe coexistence policy to the first radio coexistence managementcontroller 224 and the second radio management controller 226. Thecoexistence policy can be provided to the first radio 218 and secondradio 220 via an interface(s) between the processor 210 and the radios.

The first radio 218 and/or the second radio 220 can exchange stateinformation via the interface 222 to facilitate implementation of thecoexistence policy by the first radio coexistence management controller224 and second radio coexistence management controller 226. Thus, forexample, operation 520 can include the second radio 220 providing stateinformation for the second radio 220 to the first radio 218 via theinterface 222. The state information can, for example, include anindication of an interference condition that may be experienced by thesecond radio 220. The state information can additionally oralternatively include operating state information indicating whether thesecond radio 220 is receiving or transmitting data during one or moretime periods. It will be appreciated that the method can include thefirst radio 218 providing such state information to the second radio 220in addition to or in lieu of operation 520.

Operation 530 can include the first radio coexistence managementcontroller 224 using the state information received in operation 520 tocontrol operation of the first radio 218 in accordance with thecoexistence policy to mitigate interference with the second radio 220.Operation 530 can additionally or alternatively include the first radiocoexistence management controller 224 using measurements that can bemade by the first radio 218 to control operation of the first radio 218.For example, if the first radio 218 is an aggressor radio, such as acellular radio, and the second radio 220 is a victim radio, such as aradio implementing an ISM band wireless communication technology, andthe coexistence policy defines that the second radio 220 has priorityover the first radio 218 in a given scenario, the first radiocoexistence management controller 224 can control data transmission bythe first radio 218 to mitigate interference with data reception by thesecond radio 220. In this regard, the first radio coexistence managementcontroller 224 can use any hardware-based and/or software-basedtechnique for mitigating interference, such as adjusting filtering oftransmissions, adjusting linearity of RF components, time domain sharingtechniques, frequency domain exclusion techniques, power domaintechniques, some combination thereof, or the like to mitigateinterference with reception by the second radio 220. It will beappreciated, however, that other scenarios are contemplated within thescope of the disclosure, including the first radio 218 being a victimradio, the second radio 220 being an aggressor radio, the first radio218 using a wireless communication technology other than cellular, thesecond radio 220 using a non-ISM band wireless communication technology,the first radio 218 having priority over the second radio 220,coordination with one or more further co-located radios, or somecombination thereof.

It will be appreciated that the method can include the second radiocoexistence management controller 226 controlling operation of thesecond radio 220 in accordance with the coexistence policy in additionto or in lieu of operation 530. In this regard, the second radiocoexistence management controller 226 can use state information for thefirst radio 218 that can be received via the interface 222 and/ormeasurements that can be made by the second radio 220 to controloperation of the second radio 220 in accordance with the coexistencepolicy.

FIG. 6 illustrates a flowchart according to an example method that canbe performed by a processor of a wireless communication device forfacilitating in-device coexistence between radios according to someexample embodiments. In this regard, FIG. 6 illustrates operations thatcan, for example, be performed by processing circuitry 210, processor212, coexistence scenario manager 216, HOST 302, coexistence scenariomanager 310, some combination thereof, or the like.

Operation 600 can include the processor defining a coexistence policyfor the first radio 218 and the second radio 220. The coexistence policycan, for example, define one or more priorities between radios. It willbe appreciated that in devices having three or more radios, operation600 can include defining a coexistence policy including the additionalradios. Operation 610 can include the processor providing thecoexistence policy to the first radio 218 and the second radio 220 viaan interface(s) between the processor and the radios. The coexistencepolicy can configure coexistence management controllers on the radios(e.g., first radio coexistence management controller 224, second radiocoexistence management controller 226, real time coex manager 322, realtime coex manager 328, real time coex manager 330, and/or the like) tocontrol operation of the radios based at least in part on stateinformation that can be exchanged between the radios.

FIG. 7 illustrates a flowchart according to another example method thatcan be performed by a processor of a wireless communication device forfacilitating in-device coexistence between radios according to someexample embodiments. In this regard, FIG. 7 illustrates an examplemethod in which a coexistence policy can be defined based at least inpart on a current use case context of a wireless communication device.Processing circuitry 210, processor 212, coexistence scenario manager216, HOST 302, coexistence scenario manager 310, some combinationthereof, or the like can, for example, provide means for performing theoperations illustrated in and described with respect to FIG. 7.

Operation 700 can include the processor determining a use case contextfor the wireless communication device. The use case context can, forexample, be determined based at least in part on a set of applications(e.g., applications 312) active on the device and/or a usage state ofone or more such active applications. Operation 710 can include theprocessor defining a coexistence policy for the first radio 218 and thesecond radio 220 based at least in part on the determined use casecontext. The coexistence policy can, for example, define one or morepriorities between radios. Thus, for example, one radio may havepriority given a first use case context and another radio may havepriority given a second use case context. It will be appreciated that indevices having three or more radios, operation 710 can include defininga coexistence policy including the additional radios. Operation 720 caninclude the processor providing the coexistence policy to the firstradio 218 and the second radio 220 via an interface(s) between theprocessor and the radios. In this regard, operation 720 can correspondto operation 610 as described above. As use case context of the devicechanges over time, the method can return to operation 700, and themethod can be repeated such that a new coexistence policy can be definedin response to a change in use case context.

FIG. 8 illustrates a flowchart according to an example method that canbe performed by a radio for facilitating in-device coexistence betweenradios according to some example embodiments. In this regard, FIG. 8illustrates a method that can be performed by the first radio 218,second radio 220, cellular radio 304, GNSS radio 306, BT/Wi-Fi comboradio 308, and/or other radio that can be implemented on a wirelesscommunication device. A coexistence management controller (e.g., firstradio coexistence management controller 224, second radio coexistencemanagement controller 226, real time coex manager 322, real time coexmanager 328, real time coex manager 330, and/or the like) can, forexample, provide means for performing one or more of the operationsillustrated in and described with respect to FIG. 8.

Operation 800 can include a radio receiving a coexistence policy via aninterface between the radio and a host processor, such as the processor212, HOST 302, or the like. The method can optionally further includeoperation 810, which can include the radio performing measurements. Themeasurements can, for example, include performing measurements ofobserved interference conditions, such as any observed errors in datareception, leakage from adjacent bands, harmonics, and/or other signalsor frequencies that may result from operation of a co-located radio(s)and that may interfere with operation of the radio. Operation 820 caninclude the radio sending state information for the radio to aco-located radio(s) via an interface, such as interface 222 or interface326, between the radio and the co-located radio(s). The stateinformation can, for example, include operating state informationindicative of whether the radio is receiving or transmitting data duringone or more time periods. In embodiments including operation 810, thestate information can additionally or alternatively include anindication of an interference condition experienced by the radio, as canbe defined based on measurements that can be made by the radio.

FIG. 9 illustrates a flowchart according to another example method thatcan be performed by a radio for facilitating in-device coexistencebetween radios according to some example embodiments. In this regard,FIG. 9 illustrates a method that can be performed by the first radio218, second radio 220, cellular radio 304, GNSS radio 306, BT/Wi-Ficombo radio 308, and/or other radio that can be implemented on awireless communication device. A coexistence management controller(e.g., first radio coexistence management controller 224, second radiocoexistence management controller 226, real time coex manager 322, realtime coex manager 328, real time coex manager 330, and/or the like) can,for example, provide means for performing one or more of the operationsillustrated in and described with respect to FIG. 9.

Operation 900 can include the radio receiving a coexistence policy viaan interface between the radio and a host processor, such as theprocessor 212, HOST 302, or the like. Operation 920 can include theradio receiving state information for a co-located radio via aninterface, such as interface 222 or interface 326, between the radio andthe co-located radio. Thus, for example, operation 920 can include theradio receiving state information that can be provided by the co-locatedradio in accordance with performance of operation 820 by the co-locatedradio.

Operation 930 can include the radio using the state information for theco-located radio to control operation of the radio in accordance withthe coexistence policy to mitigate interference with the co-locatedradio. It will be appreciated that the radio can use any hardware-basedand/or software-based technique for mitigating interference, such asadjusting filtering of transmissions, adjusting linearity of RFcomponents, time domain sharing techniques, frequency domain exclusiontechniques, power domain techniques, some combination thereof, or thelike to mitigate interference with the co-located radio.

The various aspects, embodiments, implementations or features of thedescribed embodiments can be used separately or in any combination.Various aspects of the described embodiments can be implemented bysoftware, hardware or a combination of hardware and software. Thedescribed embodiments can also be embodied as computer readable code ona computer readable medium for controlling manufacturing operations oras computer readable code on a computer readable medium for controllinga manufacturing line. The computer readable medium is any data storagedevice that can store data which can thereafter be read by a computersystem. Examples of the computer readable medium include read-onlymemory, random-access memory, CD-ROMs, HDDs, DVDs, magnetic tape, andoptical data storage devices. The computer readable medium can also bedistributed over network-coupled computer systems so that the computerreadable code is stored and executed in a distributed fashion.

In the foregoing detailed description, reference was made to theaccompanying drawings, which form a part of the description and in whichare shown, by way of illustration, specific embodiments in accordancewith the described embodiments. Although these embodiments are describedin sufficient detail to enable one skilled in the art to practice thedescribed embodiments, it is understood that these examples are notlimiting; such that other embodiments may be used, and changes may bemade without departing from the spirit and scope of the describedembodiments.

Further, the foregoing description, for purposes of explanation, usedspecific nomenclature to provide a thorough understanding of thedescribed embodiments. However, it will be apparent to one skilled inthe art that the specific details are not required in order to practicethe described embodiments. Thus, the foregoing descriptions of specificembodiments are presented for purposes of illustration and description.The description of and examples disclosed with respect to theembodiments presented in the foregoing description are provided solelyto add context and aid in the understanding of the describedembodiments. The description is not intended to be exhaustive or tolimit the described embodiments to the precise forms disclosed. It willbe apparent to one of ordinary skill in the art that many modifications,alternative applications, and variations are possible in view of theabove teachings. In this regard, one of ordinary skill in the art willreadily appreciate that the described embodiments may be practicedwithout some or all of these specific details. Further, in someinstances, well known process steps have not been described in detail inorder to avoid unnecessarily obscuring the described embodiments.

What is claimed is:
 1. A wireless communication device comprising: aprocessor; a first radio comprising a first coexistence managementcontroller, the first radio being coupled to the processor via aninterface between the processor and the first radio; and a second radiocomprising a second coexistence management controller, the second radiobeing coupled to the first radio via a second interface between thefirst radio and the second radio, wherein: the processor is configuredto define a coexistence policy for the first radio and the second radioand to provide the coexistence policy to the first coexistencemanagement controller via the interface between the processor and thefirst radio; the second radio is configured to provide state informationof the second radio to the first radio via the second interface betweenthe first radio and the second radio; and the first coexistencemanagement controller is configured to use the state information of thesecond radio provided by the second radio to control operation of thefirst radio in accordance with the coexistence policy to mitigateinterference with the second radio, wherein the state information of thesecond radio is provided to the first radio more frequently than thecoexistence policy is provided to the first radio by the processor. 2.The wireless communication device of claim 1, wherein the stateinformation of the second radio comprises an indication of aninterference condition experienced by the second radio, and wherein theindication of the interference condition is determined by a radiomeasurement made by the second radio.
 3. The wireless communicationdevice of claim 1, wherein the state information of the second radiocomprises an operating state indicative of whether the second radio isreceiving or transmitting data during a time period.
 4. The wirelesscommunication device of claim 1, wherein the coexistence policy definesa priority between the first radio and the second radio.
 5. The wirelesscommunication device of claim 1, wherein the first radio implements acellular communication technology, and wherein the second radioimplements one or more of a wireless local area network (WLAN)communication technology or a wireless personal area network (WPAN)communication technology.
 6. The wireless communication device of claim1, wherein the processor is further configured to: determinecorresponding use case information based on active applications;leverage knowledge of states of the active applications to derive aglobal view of wireless communication device usage and determine a usecase context for the wireless communication device; and define thecoexistence policy based at least in part on the determined use casecontext, wherein a different coexistence policy is defined for a firstuse case context than for a second use case context.
 7. The wirelesscommunication device of claim 6, wherein the coexistence policy definesone or more priorities between the first radio and the second radiogiven the determined use case context.
 8. The wireless communicationdevice of claim 1, wherein: the processor is further configured toprovide the coexistence policy to the second coexistence managementcontroller via a third interface between the processor and the secondradio; the first radio is further configured to provide stateinformation of the first radio to the second radio via the secondinterface between the first radio and the second radio; and the secondcoexistence management controller is configured to use the stateinformation of the first radio provided by the first radio to controloperation of the second radio in accordance with the coexistence policy,wherein the state information of the first radio is provided to thesecond radio more frequently than the coexistence policy is provided tothe second radio by the processor.
 9. The wireless communication deviceof claim 1, wherein the first coexistence management controller isconfigured to use the state information of the second radio to controloperation of the first radio in accordance with the coexistence policyat least in part by modifying filtering applied to a transmission by thefirst radio.
 10. The wireless communication device of claim 1, whereinthe first coexistence management controller is further configured to useradio measurements made by the first radio to further control operationof the first radio in accordance with the coexistence policy in order tomitigate interference with the second radio.
 11. The wirelesscommunication device of claim 1, wherein the first coexistencemanagement controller is configured to adjust linearity of RF componentsof the first radio to mitigate effects of intermodulation distortionand/or harmonic distortion interference with the second radio.
 12. Amethod for facilitating coexistence between wireless communicationtechnologies on a wireless communication device that includes aprocessor, a first radio, and a second radio, the method comprising:defining, by the processor, a coexistence policy for the first radio andthe second radio; providing, by the processor, the coexistence policy toa first coexistence management controller of the first radio via aninterface between the processor and the first radio; providing, by thesecond radio, state information of the second radio to the first radiovia a second interface between the first radio and the second radio; andusing, by the first coexistence management controller of the firstradio, the state information of the second radio to control operation ofthe first radio in accordance with the coexistence policy, wherein thestate information of the second radio is provided to the first radiomore frequently than the coexistence policy is provided to the firstradio by the processor.
 13. The method of claim 12, wherein the stateinformation of the second radio comprises one or more of an indicationof an interference condition experienced by the second radio or anoperating state indicative of whether the second radio is receiving ortransmitting data during a time period.
 14. The method of claim 12,wherein the coexistence policy prioritizes the second radio over thefirst radio, and wherein the first coexistence management controller ofthe first radio uses the state information of the second radio tocontrol operation of the first radio by at least using the stateinformation of the second radio to control data transmission by thefirst radio to mitigate interference with data reception by the secondradio.
 15. The method of claim 12, wherein the first radio implements acellular communication technology, and wherein the second radioimplements a wireless communication technology using an Industrial,Scientific, and Medical (ISM) band.
 16. The method of claim 12, furthercomprising: by the processor: determining a use case context of thewireless communication device; and defining the coexistence policy basedat least in part on the determined use case context, wherein a differentcoexistence policy is defined for a first use case context than for asecond use case context.
 17. The method of claim 12, further comprising:providing, by the processor, the coexistence policy to a secondcoexistence management controller on the second radio via a thirdinterface between the processor and the second radio; and controllingoperation of the second radio, by the coexistence management controllerof the second radio, in accordance with the coexistence policy.
 18. Themethod of claim 17, further comprising: providing, by the first radio,state information of the first radio to the second radio via the secondinterface between the first radio and the second radio; and using thestate information of the first radio provided by the first radio, by thesecond coexistence management controller of the second radio, to controloperation of the second radio in accordance with the coexistence policy.19. A method for facilitating coexistence between wireless communicationtechnologies on a wireless communication device, the method comprising:by a processor: defining a coexistence policy for a first radio and asecond radio co-located on the wireless communication device; andproviding the coexistence policy to the first radio via an interfacebetween the processor and the first radio to configure a firstcoexistence management controller on the first radio to controloperation of the first radio in accordance with the coexistence policybased at least in part on state information of the first radio providedto the first radio by the second radio via a second interface betweenthe first radio and the second radio, wherein the state information ofthe second radio is provided to the first radio more frequently than thecoexistence policy is provided to the first radio by the processor. 20.The method of claim 19, further comprising: by the processor:determining a use case context of the wireless communication device; anddefining the coexistence policy based at least in part on the determineduse case context, wherein a different coexistence policy is defined fora first use case context than for a second use case context.